Component org.nuxeo.ecm.directory.DirectoryServiceImpl
In bundle org.nuxeo.ecm.directory
Documentation
The directory service holds registered directories.
Requirements
Resolution Order
772
The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime
framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.
Start Order
743
(Declared Start Order: 97)
The start order represents the order in which this component has been started by the Nuxeo Runtime framework.
This number is interesting to tweak if your Java component interacts with other components, and needs to be started before or after another one.
It can be changed by implementing the method "Component#getApplicationStartedOrder()" on your Java component: components are sorted according to this reference value, in increasing order.
The default value is 1000, and the repository initialization uses number 100. Negative values can also be used.
Implementation
Class:
org.nuxeo.ecm.directory.DirectoryServiceImpl
Services
Extension Points
Contributions
XML Source
<?xml version="1.0"?>
<component name="org.nuxeo.ecm.directory.DirectoryServiceImpl">
<!-- The cache service must be started before me: TODO use a start level dependency? -->
<require>org.nuxeo.ecm.core.cache.CacheService</require>
<require>org.nuxeo.runtime.cluster.ClusterService</require>
<implementation class="org.nuxeo.ecm.directory.DirectoryServiceImpl" />
<service>
<provide interface="org.nuxeo.ecm.directory.api.DirectoryService" />
</service>
<documentation>
The directory service holds registered directories.
</documentation>
<extension-point name="factoryDescriptor">
<documentation>
This extension point is obsolete.
</documentation>
<object class="org.nuxeo.ecm.directory.DirectoryFactoryDescriptor" />
</extension-point>
<extension target="org.nuxeo.runtime.EventService" point="listeners">
<listener class="org.nuxeo.ecm.directory.DirectoryCacheFlusher">
<topic>org.nuxeo.runtime.reload</topic>
</listener>
</extension>
</component>